Illustrating the Concept of Operations ( CONOPs ) Continuum and its Relationship to the Acquisition

Though consistently noted as critical to successful system design and implementation, the Concept of Operations (CONOPs) artifact appears to be underutilized. This report demystifies the CONOPs artifact. It delves into the barriers that prevent optimal use of CONOPs and presents a framework for incorporating an “integrated” CONOPs into the Defense Acquisition Lifecycle. Introduction The ability of development programs to avoid challenges associated with schedule, budget, and technical performance has been consistently poor (Turner, Verma, & Weitekamp, 2009, pg 7). A recent FAA sponsored study noted that in order to avoid these pitfalls, “one of the most significant artifacts is the creation of a CONOPs” (Turner et. al., 2009, pg 27). The report further noted the need to have “alignment between the evolving CONOPs, the [Enterprise Architecture], and the governance system...” (Turner et. al., 2009, p 32). The Manual for the Operation of The Joint Capabilities Integration and Development System (JCIDS, 2009) provides an illustration of the alignment of the enterprise architecture and the governance system by connecting JCIDS activities with milestone decisions. While important, this illustration is missing the alignment of a critical system success component, the CONOPs document. In order to encourage successful system development and acquisition we must understand the context of the CONOPs as it relates to the larger total acquisition lifecycle.